Conversation
| </choicegroup> | ||
| </multiplechoiceresponse> | ||
| <problem display_name="Ensure Your Write Access is Set" markdown="null" showanswer="" submission_wait_seconds="0" weight="1.0"><multiplechoiceresponse> | ||
| <p>If you have not already done so, file a <a href="https://github.com/openedx/axim-engineering/issues/new/choose">Axim Access/Config GitHub request</a> for adding access for yourself for whichever repo(s) you should get access to. Include a link to your nomination thread and tag the CC who nominated you.</p><p>Once you've received confirmation that your access is set, please visit each repository you were nominated to be a Core Contributor for and ensure you have write access. This is easy to do by navigating to any open PR and checking that the "merge" button is visible underneath the automated test check reporting.</p><label>I have done this, or it has already been done.</label><choicegroup><choice correct="false"><div>I'll do it later</div></choice><choice correct="true"><div>Yes</div></choice><choice correct="false"><div>I'll never do it</div></choice></choicegroup></multiplechoiceresponse> |
There was a problem hiding this comment.
as the onboarding runbook is currently written, this creates a catch-22. they can't check their access until they've been granted it, and we don't grant it until the course (including this question) is complete.
There was a problem hiding this comment.
ugh! What do you think it should say? maybe just "After your access has been granted, be sure to remember to double-check your access"?
There was a problem hiding this comment.
I like that. You could have the answers be:
- OK, I'll double-check my access as soon as it's granted ✅
- Nah, I'll just wait until there's a problem ❌
839d01c to
8487632
Compare
| <choice correct="false">I'll never do it</choice> | ||
| </choicegroup> | ||
| </multiplechoiceresponse> | ||
| <problem display_name="Ensure Your Write Access is Set" markdown="null" showanswer="" submission_wait_seconds="0" weight="1.0"><multiplechoiceresponse> |
There was a problem hiding this comment.
the pretty xml formatting was nice, consider preserving that? but OTOH, completely understood if you think it's not worth the effort, you're the one maintaining this--up to you.
There was a problem hiding this comment.
At some point, Studio exports quit pretty-printing. I have been just raw-exporting these from Studio. cc @ormsbee
There was a problem hiding this comment.
(I don't do any editing in the XML)
No description provided.